PR #1291 — validate-patch

PR: #1291

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: N/A — click to expand

🔍 Patch Validation

PR: #1291 - QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Upstream commit: N/A (vendor-only commit)
Verdict: ⏭️ SKIP (validation not applicable)

Commit Message

Check	Status	Note
Subject matches upstream	N/A	QCLINUX: prefix indicates vendor-only commit
Body preserves rationale	N/A	No upstream source to compare against
Fixes tag present/correct	N/A	No Fixes tag; vendor-only addition
Authorship preserved	N/A	Original vendor contribution
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi	⏭️ SKIP	Vendor-only device tree additions (GMSL deserializer and sensor nodes)

Verdict

This is a vendor-only commit (QCLINUX: prefix) adding Talos-specific camera hardware nodes. No upstream validation is applicable or required. The commit is properly formatted for vendor-only changes with appropriate sign-off and internal CR tracking.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

PR #1291 — checker-log-analyzer

PR: #1291
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/26756170574

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1291 — QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26756170574

Checker	Result	Summary
checkpatch	❌	3 warnings: undocumented DT compatible, missing commit descriptions
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Graph port errors in new GMSL deserializer node
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	All 5 commits missing required prefix
tag-check	❌	All 5 commits missing required prefix (target branch: tech/overlay/dt)

---

❌ checkpatch

Root cause: Three commits have style issues: one undocumented DT compatible string and two commits with missing commit descriptions.

Failure details:

Commit abc71de7617a ("QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor"):

WARNING: DT compatible string "qcom,cam-gmsl-sensor" appears un-documented -- check ./Documentation/devicetree/bindings/
#69: FILE: arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:188:
+		compatible = "qcom,cam-gmsl-sensor";

Commit b7de1d752e12 ("QCLINUX: arm64: dts: qcom: Enable combo mode for CSI1 port..."):

WARNING: Missing commit description - Add an appropriate one

Commit fc647a8ed68a ("QCLINUX: arm64: dts: qcom: Fix GPIO free and acquire logic..."):

WARNING: Missing commit description - Add an appropriate one

Fix:

1. For undocumented compatible string — Add binding documentation:

   # Create Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml
   # or add "qcom,cam-gmsl-sensor" to an existing camera sensor binding

2. For missing commit descriptions — The commit subjects are too long and contain the description. Move the description to the commit body:

   git rebase -i <base_sha>   # mark commits as 'edit'
   # For b7de1d752e12:
   git commit --amend
   # Change subject to: "QCLINUX: arm64: dts: qcom: Enable combo mode for CSI1 port"
   # Move rest to body: "In order to enable combo mode on CSI1 mode, resources needs..."
   
   # For fc647a8ed68a:
   git commit --amend
   # Change subject to: "QCLINUX: arm64: dts: qcom: Fix GPIO free and acquire logic"
   # Move rest to body: "Prevent GPIOs managed by pinctrl from being requested..."
   
   git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git df3ae9703774..2d37d93c0a70

---

❌ dtb-check

Root cause: The new port@0 node in qcom,cam-gmsl-deserializer0 is missing required #address-cells and #size-cells properties for graph port nodes, causing reg_format, avoid_default_addr_size, and graph_port warnings.

Failure details:

arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:178:4:

Warning (reg_format): /fragment@0/__overlay__/qcom,cci@ac4a000/qcom,cam-gmsl-deserializer0/port@0:reg: 
  property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Warning (avoid_default_addr_size): ...port@0: Relying on default #address-cells value
Warning (avoid_default_addr_size): ...port@0: Relying on default #size-cells value

Warning (graph_port): ...port@0: graph node '#address-cells' is -1, must be 1
Warning (graph_port): ...port@0: graph node '#size-cells' is -1, must be 0

Fix:

Add explicit #address-cells and #size-cells to the port@0 node in arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:177:

 	/* GMSL deserializer 0 - max9296a */
 	qcom,cam-gmsl-deserializer0 {
 		cell-index = <2>;
 		...
 		status = "ok";
 
+		#address-cells = <1>;
+		#size-cells = <0>;
+
 		port@0 {
 			reg = <0>;
 			deser0_port0: endpoint {
 				remote-endpoint = <&gmsl_sensor0_ep>;
 			};
 		};
 	};

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/talos-evk-camx.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/qcs615-ride-camx.dtb

---

❌ check-patch-compliance

Root cause: All 5 commits use the QCLINUX: prefix, which is not in the allowed list for check-patch-compliance. The checker only accepts FROMLIST:, FROMGIT:, UPSTREAM:, and BACKPORT:.

Failure details:

Checking commit: arm64: dts: qcom: hamoa: add CAMX EL2 overlay
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: add Purwa CAMX EL2 overlay
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: Enable combo mode for CSI1 port...
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: Fix GPIO free and acquire logic...
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Commit summary does not start with a required prefix

Fix:

This is a known limitation of check-patch-compliance — it does not accept vendor-only prefixes like QCLINUX: or PENDING:. These commits are vendor-specific DTS additions with no upstream equivalent.

Options:

1. If these patches have been posted upstream → change prefix to FROMLIST: and add Link: <lore-url> to commit body.
2. If vendor-only → this checker will always fail. The QCLINUX: prefix is correct for vendor-only changes, but check-patch-compliance enforces upstream-linkable prefixes only.

Note: The first commit (arm64: dts: qcom: hamoa: add CAMX EL2 overlay) is missing any prefix — add QCLINUX: to the subject.

---

❌ tag-check

Root cause: The PR targets branch tech/overlay/dt, which is not qcom-next or qcom-next-staging. All commits merged into this branch must start with a valid prefix tag. Five commits are missing or using invalid prefixes.

Failure details:

1. Commit a7c58823f27f ("arm64: dts: qcom: hamoa: add CAMX EL2 overlay") — no prefix
2. Commit 8d6e4e962e7e ("QCLINUX: arm64: dts: qcom: add Purwa CAMX EL2 overlay") — QCLINUX: is valid ✅
3. Commit b7de1d752e12 ("QCLINUX: arm64: dts: qcom: Enable combo mode for CSI1 port...") — QCLINUX: is valid ✅
4. Commit fc647a8ed68a ("QCLINUX: arm64: dts: qcom: Fix GPIO free and acquire logic...") — QCLINUX: is valid ✅
5. Commit abc71de7617a ("QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor") — QCLINUX: is valid ✅

Fix:

Add QCLINUX: prefix to the first commit:

git rebase -i <base_sha>   # mark commit a7c58823f27f as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: hamoa: add CAMX EL2 overlay"
git rebase --continue

Valid prefixes for tech/overlay/dt branch:

• FROMLIST: — Posted to mailing list
• FROMGIT: — In a maintainer tree
• UPSTREAM: — Merged into Linus's tree
• BACKPORT: — Backported with modifications
• QCLINUX: — Vendor-only, no upstream
• PENDING: — Work-in-progress
• WORKAROUND: — Temporary fix

---

Verdict

Fix 4 blockers before merge:

1. ❌ checkpatch — Add DT binding for qcom,cam-gmsl-sensor and fix commit descriptions (move long subjects to body)
2. ❌ dtb-check — Add #address-cells = <1>; #size-cells = <0>; to qcom,cam-gmsl-deserializer0 node
3. ⚠️ check-patch-compliance — Known limitation for QCLINUX: prefix; will always fail for vendor-only commits
4. ❌ tag-check — Add QCLINUX: prefix to first commit (arm64: dts: qcom: hamoa: add CAMX EL2 overlay)

PR #1291 — validate-patch

PR: #1291

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1291 - QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Upstream commit: N/A (vendor-only)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit with QCLINUX: prefix
Body preserves rationale	✅	Clear description of added hardware nodes
Fixes tag present/correct	N/A	New feature addition, not a fix
Authorship preserved	✅	Author: Milen Mitkov mmitkov@qti.qualcomm.com
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi	✅	Adds GMSL deserializer and sensor nodes; clean addition

Commit Message Quality

• Subject line: Properly formatted with QCLINUX: prefix indicating vendor-specific change
• Body: Provides clear rationale - adds deserializer and camera sensor nodes for Talos platform
• CRs-Fixed tag: Present (4555961) - appropriate for internal tracking
• Signed-off-by: Present and matches author

Diff Analysis

The patch adds 54 lines to talos-camera-sensor.dtsi:

• GMSL deserializer node (qcom,cam-gmsl-deserializer0): Properly configured with cell-index=2, power supplies, GPIOs, clocks, and port endpoint
• GMSL sensor node (qcom,cam-gmsl-sensor0): Basic structure with cell-index=3, compatible string, and port endpoint
• Device tree structure: Follows Qualcomm camera subsystem conventions
• No upstream conflicts: Vendor-specific hardware configuration

Verdict

Merge as-is — this is a well-formed vendor-only device tree addition with proper commit message formatting and clean diff.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

PR #1291 — checker-log-analyzer

PR: #1291
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/26756170574

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1291 - QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26756170574

Checker	Result	Summary
checkpatch	❌	Undocumented DT compatible string warning
dt-binding-check	✅	No DT binding changes
dtb-check	❌	Multiple DT schema validation errors for new nodes
sparse-check	⏭️	Skipped (no C code changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Missing FROMLIST:/UPSTREAM:/BACKPORT: prefix
tag-check	N/A	Not applicable for tech/overlay/dt branch
qcom-next-check	N/A	Not applicable for tech/overlay/dt branch

---

❌ checkpatch

Root cause: The compatible string qcom,cam-gmsl-sensor is not documented in DT bindings.

Failure details:

WARNING: DT compatible string "qcom,cam-gmsl-sensor" appears un-documented -- check ./Documentation/devicetree/bindings/
#69: FILE: arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:188:
+		compatible = "qcom,cam-gmsl-sensor";

abc71de7617abf50634045d2255f0fa39ea96fd5 total: 0 errors, 1 warnings, 0 checks, 60 lines checked

Fix: Add a device tree binding document for the GMSL sensor at Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml before using this compatible string, or use an existing documented compatible if appropriate.

Reproduce locally:

./scripts/checkpatch.pl --strict --git HEAD~1..HEAD

---

❌ dtb-check

Root cause: The new GMSL deserializer and sensor nodes violate DT schema requirements: missing #address-cells, #size-cells, and ranges properties for graph port nodes, and the compatible string has no matching schema.

Failure details:

arch/arm64/boot/dts/qcom/talos-evk-camx.dtb: /soc@0/qcom,cci@ac4a000/qcom,cam-gmsl-sensor0: failed to match any schema with compatible: ['qcom,cam-gmsl-sensor']

../arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:177.10-182.5: Warning (graph_port): /fragment@0/__overlay__/qcom,cci@ac4a000/qcom,cam-gmsl-deserializer0/port@0: graph node '#address-cells' is -1, must be 1

../arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi:177.10-182.5: Warning (graph_port): /fragment@0/__overlay__/qcom,cci@ac4a000/qcom,cam-gmsl-deserializer0/port@0: graph node '#size-cells' is -1, must be 0

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/talos-evk-camx.dtb: qcom,cci@ac4a000 (qcom,cci): qcom,cam-gmsl-sensor0: 'ranges' is a required property

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/talos-evk-camx.dtb: qcom,cci@ac4a000 (qcom,cci): qcom,cam-gmsl-deserializer0: 'ranges' is a required property

Fix:

1. Add DT binding schema for qcom,cam-gmsl-sensor (same as checkpatch requirement)
2. Add #address-cells = <1>; and #size-cells = <0>; to the port@0 node in qcom,cam-gmsl-deserializer0
3. Verify the parent CCI node structure matches the expected schema for child nodes

Reproduce locally:

make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/media/

---

❌ check-patch-compliance

Root cause: All 5 commits in this PR lack the required subject prefix (FROMLIST:, UPSTREAM:, or BACKPORT:) for the tech/overlay/dt branch.

Failure details:

Checking commit: arm64: dts: qcom: hamoa: add CAMX EL2 overlay
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: add Purwa CAMX EL2 overlay
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: Enable combo mode for CSI1 port...
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: Fix GPIO free and acquire logic...
Commit summary does not start with a required prefix

Checking commit: QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Commit summary does not start with a required prefix

Fix: Reword all commit subjects to start with one of the required prefixes:

• FROMLIST: if the patch is posted to an upstream mailing list but not yet merged
• UPSTREAM: if the patch is already merged upstream
• BACKPORT: if the patch is a backport from a newer kernel version
• QCLINUX: appears to not be recognized; use one of the above instead

Example for the PR commit:

FROMLIST: arm64: dts: qcom: talos: Add GMSL deserializer and sensor

Reproduce locally:

# Check if your commit follows the required prefix pattern
git log --oneline -5 | grep -E '^[a-f0-9]+ (FROMLIST|UPSTREAM|BACKPORT):'

---

Verdict

3 blockers must be fixed before merge:

1. Add DT binding documentation for qcom,cam-gmsl-sensor compatible string
2. Fix DT schema violations in the GMSL deserializer/sensor nodes (add required properties)
3. Update commit message prefixes for all 5 commits to use FROMLIST:/UPSTREAM:/BACKPORT: instead of QCLINUX:

qli-2.0 GA pull-request freeze

🔨 Build Failure Analysis — PR #1291

PR: #1291
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621864602

Verdict

This is not a PR-introduced failure. The build failed during the automerge phase due to a pre-existing merge conflict in a file unrelated to this PR's changes.

📎 Detailed analysis: Full report

🔨 Build Failure Analysis — PR #1291

PR: #1291
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621864602

Verdict

This is not a compilation failure. The build failed during the automerge phase due to a pre-existing merge conflict in include/dt-bindings/mailbox/qcom-ipcc.h when integrating the topic/tech/overlay/dt branch. The PR itself only modifies arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi and does not introduce this conflict. The PR changes are syntactically valid device tree additions.

📎 Detailed analysis: Full report

PR #1291 — validate-patch

PR: #1291

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1291 - QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Upstream commit: N/A (vendor-only commit)
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit (QCLINUX: prefix)
Body preserves rationale	✅	Clear description of added hardware nodes
Fixes tag present/correct	N/A	Not a fix; new feature addition
Authorship preserved	✅	Author: Milen Mitkov mmitkov@qti.qualcomm.com
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi	⚠️	Uses non-standard status = "ok" instead of "okay" (2 instances)

Issues

Device Tree binding inconsistency:

• Lines 56 and 75: Both new nodes use status = "ok" instead of the standard status = "okay"
• Per devicetree specification (ePAPR/DTSpec), the status property should use "okay" not "ok"
• Existing code in the same file (line 24) correctly uses status = "okay"
• This inconsistency may cause issues with DT validation tools and is not aligned with kernel DT conventions

Node naming:

• Node names qcom,cam-gmsl-deserializer0 and qcom,cam-gmsl-sensor0 include vendor prefix in node name, which is non-standard (vendor prefix should only be in compatible string)
• However, this appears to match existing patterns in the Qualcomm camera subsystem vendor code

Verdict

Recommend fixing the status = "ok" → status = "okay" inconsistency before merge to maintain consistency with DT standards and existing code in the same file.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

PR #1291 — checker-log-analyzer

PR: #1291
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621864874

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1291 - QCLINUX: arm64: dts: qcom: talos: Add GMSL deserializer and sensor
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27621864874

Checker	Result	Summary
checkpatch	⏭️	Not executed - automerge conflict blocked CI
dt-binding-check	⏭️	Not executed - automerge conflict blocked CI
dtb-check	⏭️	Not executed - automerge conflict blocked CI
sparse-check	⏭️	Not executed - automerge conflict blocked CI
check-uapi-headers	⏭️	Not executed - automerge conflict blocked CI
check-patch-compliance	⏭️	Not executed - automerge conflict blocked CI
tag-check	N/A	Not applicable for this branch
qcom-next-check	N/A	Not applicable - QCLINUX prefix used

❌ CI Infrastructure Failure (Automerge Conflict)

Root cause: All checker jobs failed during the automerge setup phase when attempting to merge topic/tech/overlay/dt into the integration branch. A merge conflict in include/dt-bindings/mailbox/qcom-ipcc.h prevented the integration branch from being created, which blocked all downstream checker jobs from executing.

Failure details:

2026-06-16T14:00:30.7677693Z Auto-merging include/dt-bindings/mailbox/qcom-ipcc.h
2026-06-16T14:00:30.7678321Z CONFLICT (content): Merge conflict in include/dt-bindings/mailbox/qcom-ipcc.h
2026-06-16T14:00:30.8292017Z Automatic merge failed; fix conflicts and then commit the result.
2026-06-16T14:00:30.8418585Z Merge failed, manual merge
2026-06-16T14:00:30.9998340Z automerge returned non-zero; check logs for conflicts
2026-06-16T14:00:31.0013960Z ##[error]Process completed with exit code 1.

Analysis:

• This PR modifies arch/arm64/boot/dts/qcom/talos-camera-sensor.dtsi (device tree changes only)
• The conflict is in a completely unrelated file: include/dt-bindings/mailbox/qcom-ipcc.h
• The conflict occurs when the CI attempts to merge the PR's target branch (topic/tech/overlay/dt) with the baseline integration branch
• This is NOT a problem with the PR itself - the PR's changes are clean and do not touch the conflicting file
• The conflict exists between the baseline and the topic branch, independent of this PR

Fix:

This is an infrastructure/branch maintenance issue, not a PR issue. The conflict must be resolved at the branch level:

1. Option A (Recommended): Rebase or update the topic/tech/overlay/dt branch to resolve the conflict with the baseline integration branch (f74a35752ee9fde35f8980d2635660334bff6446). This should be done by the branch maintainer.

2. Option B: If the conflict is due to parallel changes in the baseline, wait for the baseline to stabilize and re-trigger the CI.

3. Option C: Manually resolve the conflict in include/dt-bindings/mailbox/qcom-ipcc.h in the topic branch by merging or rebasing against the current baseline.

Reproduce locally:

# Clone the kernel-topics repo
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics

# Fetch the baseline and topic branch
git fetch origin topic/tech/overlay/dt
git fetch origin f74a35752ee9fde35f8980d2635660334bff6446

# Attempt the merge that CI is doing
git checkout -b test-integ f74a35752ee9fde35f8980d2635660334bff6446
git merge origin/topic/tech/overlay/dt

# You will see the conflict in include/dt-bindings/mailbox/qcom-ipcc.h
# Resolve it, then test if the PR applies cleanly on top

Verdict

This PR cannot be evaluated by CI due to an infrastructure conflict. The PR's changes themselves appear clean (device tree additions for Talos GMSL camera support), but no checkers were able to run. The conflict in include/dt-bindings/mailbox/qcom-ipcc.h must be resolved at the branch level before CI can validate this PR. Once the topic branch conflict is resolved, re-trigger the CI to get actual checker results.